Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server


Delta df to MS SQL Server Incremental Schema Migration utility

The Incremental Schema Migration utility allows you to migrate schema changes from OpenEdge to an MS SQL Server database. For example, in the process of developing an application in the Progress 4GL that you will migrate to MS SQL Server, you might want to make and test schema changes in the OpenEdge database that you want reflected in the MS SQL Server database. The utility reads an OpenEdge delta.df file that has been created using the standard incremental dump procedure. and creates a delta.sql file that contains the SQL DDL for making the changes and a delta.df file. You can then load the delta.df file into the schema holder. You can then apply the delta.sql file to the MS SQL Server database to complete the migration process.

Note: You do not make schema changes directly in the schema holder, which must remain synchronized with the MS SQL Server database. The utility uses the schema holder to determine what the MS SQL Server definitions are.

To run the Incremental Schema Migration utility:

  1. From the Data Admin main menu, choose DataServers MS SQL Server Utilities Schema Migration Tools Generate Delta.sql Progress to MSS. The following dialog box appears:
  2. Provide the information as described in Table 7–7.
  3. Table 7–7: Generate Delta.sql Progress-to-MSS utility
    Interface element
    Description
    Delta DF File
    The name of the delta.df file that was created when you ran the incremental dump routine against two OpenEdge databases. You can browse for the file name by choosing the Files button.
    Schema Holder Database
    The name of the schema holder. The schema information must match the schema of the MS SQL Server database to be updated. Progress Software Corporation recommends that you are connected to the schema holder.
    Connect parameters for Schema
    Specify these parameters to connect to the schema holder if you are not already connected.
    Logical name for MSS Database
    Specify the MS SQL Server database logical name, that is, the name by which you refer to the MS SQL Server database in your application.
    MSS Object Owner Name
    Specify the name of the MSS database object owner.
    Maximum Varchar Length
    Specify the maximum size of the VARCHAR field. Any size greater will be text. Max size is 8,000.
    Create Progress RECID field
    Leave this toggle box checked to obtain the cursor scrolling capability.
    Include default
    Check this toggle is you want the OpenEdge initial value used as the default SQL script.
    Create Shadow Columns
    This is only available if Code Page is sensitive.
    Use Sql Width
    If your OpenEdge database contains data that is larger than the display format, you can check this toggle box. Change the SQL width field in the Data Dictionary to the proper size. The utility will use the SQL width field instead of the display format.
    Create schema holder delta df
    Check this toggle box if you want the utility to generate a .df file that includes the incremental schema information. You can then load this .df file into the schema holder. By default, this toggle box is checked.

  4. Choose OK. The utility generates a delta.sql file and, optionally, a delta.df file.
  5. After running the utility, you must apply the SQL it generates to the MS SQL Server database and load the new delta.df file into the original schema holder so that it is synchronized with the modified MS SQL Server database.

The utility generates SQL that will create objects in the MS SQL Server database that are compatible with OpenEdge. It creates the same objects as the Progress-to-MSS Migration utility.

Table 7–8: MS SQL Server equivalents of OpenEdge objects 
OpenEdge object
MS SQL Server equivalents
Array
One column for each extent of the OpenEdge array.
Table
For new tables, if the Create Progress RECID Field was check, a PROGRESS_RECID column and associated triggers are created. This indexed column provides a unique key on the MS SQL Server table.

The utility ensures that the migrated objects have names that are unique to the MS SQL Server database. If you have given the object a name that is not unique, it drops characters from the end of the name and appends numbers until it creates a unique name.

Since MS SQL Server requires that index names be unique to the database, the utility appends the table name to the indexed column name to create a unique name.


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095